-
Notifications
You must be signed in to change notification settings - Fork 84
Filter by tag proposals #503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…g_proposals before filtering by query
…ssibly the slowest way of filtering.
…ent or not present.
…th mass_create_tool.py.
…ong with objects of associated classes (so far just ProblemSite).
argument types to unsigned_int.
I did some benchmarking, these are my results: The tag through and tag proposal records were randomly distributed. The tool I used for generating the data will be merged in a different PR. For data:
I got average times of:
For data:
I got average times of:
For data:
I got average times of:
It seems that the performance decrease I was worried about is negligible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
* Add the option for filtering by algorithm tags to take into account most popular tag proposals when choosing which tasks to show in the results. * Add the value `include_proposals` to be included in `?q=` for the problemset page controlling whether filtering by algorithm tags takes the most popular tag proposals into account. * Add `TestTagProposalsSearch` test class for this feature.
Closes #420. Closes #487.
Make it possible to search by algorithm tag proposals.
Includes wording change for the checkbox controlling tag proposals so Transifex will need to be updated if the change is kept.